[LINUX] Properly trigger XenbusStateClosed in blkfront
authorkfraser@localhost.localdomain <kfraser@localhost.localdomain>
Thu, 30 Nov 2006 17:34:48 +0000 (17:34 +0000)
committerkfraser@localhost.localdomain <kfraser@localhost.localdomain>
Thu, 30 Nov 2006 17:34:48 +0000 (17:34 +0000)
commitf6656783078c6a4d0c2397a24acd3774403ab42f
treee112420bccc84ae54ce682ac1cd881e8c8eeb5e7
parent671ac0de22689db93afb37dce54837641f353f46
[LINUX] Properly trigger XenbusStateClosed in blkfront

In some situations, like when error happens in block attach for
a guest in dom0, backend send us XenbusStateClosing notification.
However, as frontend were never properly initialized, it fails
to change its own state to XenbusStateClosed, leaving the system
in a dead-end state.

Signed-off-by: Glauber de Oliveira Costa <gcosta@redhat.com>
linux-2.6-xen-sparse/drivers/xen/blkfront/blkfront.c